Multi-action button for mobile devices

ABSTRACT

Systems, methods, and computer-readable media for providing a multi-action button for mobile devices are provided. Alerts are received and multi-action buttons are determined corresponding to the alerts and clinicians associated with mobile devices. The multi-action buttons are displayed on the mobile devices.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of copending U.S. application Ser.No. 15/395,603, titled “Multi-Action Button for Mobile Devices,” filedDec. 30, 2016, which is a continuation of U.S. application Ser. No.14/983,685 (issued as U.S. Pat. No. 10,379,713), titled “Multi-ActionButton for Mobile Devices,” filed Dec. 30, 2015, which is a continuationof U.S. application Ser. No. 13,711,177 (issued as U.S. Pat. No.9,280,637), titled “Multi-Action Button for Mobile Devices,” filed Dec.11, 2012, which claims the benefit of U.S. Provisional Application No.61/710,409, titled “Multi-Action Button for Mobile Devices and AttachingPatient Context to a Call History Associated With Voice Communication,”filed Oct. 5, 2012, each of which is hereby expressly incorporated byreference in its entirety.

BACKGROUND

Patient medical information, such as that contained in the EMR, allowshealth care providers to provide continuity of care to patients. Thus,it is critical for clinicians providing care to patients to review andcollaborate with other clinicians for each patient's medical record.However, these collaborations, while important to providing care forpatients, often goes undocumented because the ability to track mobilevoice communication as well as the content discussed is not currentlyavailable. This results in confusion and an inability to reference thedetails (e.g. patient name, relevant alerts, and the like) of a mobilevoice call and leaves the clinician and healthcare entity unable toappropriately track such information that may otherwise be useful inanalytics, tracking patient progress, billing, reimbursement, schedulingstaff, and patient acuity.

Further, when receiving alerts regarding a particular patient, it iscritical that these alerts are acknowledged in a timely manner. Often,it is necessary for an additional action to be taken in addition toacknowledging the alert. For example, the responding clinician may needto acknowledge (i.e., accept) the alert and call or text anotherclinician. Unfortunately, displays of current mobile devices arecluttered with option buttons which results in confusion and time lostpondering the correct action.

SUMMARY

This summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used as an aid in determining the scope of the claimed subjectmatter.

Embodiments of the present invention relate to providing a multi-actionbutton for mobile devices. More particularly, an alert is received and amulti-action button is determined corresponding to the alert and aclinician associated with a mobile device and the multi-action button isdisplayed on the mobile device.

Accordingly, in one embodiment, computer storage media storingcomputer-executable instructions that, when executed by one or morecomputing devices, cause the one or more computing devices to perform amethod that facilitates providing a multi-action button for mobiledevices is provided. An alert is received at a mobile device associatedwith a clinician. A multi-action button is determined that correspondsto the alert and a role associated with the clinician. The multi-actionbutton is displayed on the mobile device.

In another embodiment, a computer system to facilitate providing amulti-action button for mobile devices is provided. The computer systemcomprises a processor coupled to a computer storage medium, the computerstorage medium having stored thereon a plurality of computer softwarecomponents executable by the processor. An alert component receives analert on a mobile device associated with a clinician. A multi-actionbutton component determines a multi-action button that corresponds tothe alert and a role associated with the clinician. A display componentdisplays the multi-action button on the mobile device.

In another embodiment, computer storage media having computer-executableinstructions embodied thereon that, when executed, produce a graphicaluser interface (GUI) to facilitate providing a multi-action button formobile devices is provided. An alert display area that displays an alerton a mobile device associated with a clinician. A multi-action displayarea displays a multi-action button that corresponds to the alert and arole associated with the clinician.

BRIEF DESCRIPTION OF THE DRAWING

The present invention is described in detail below with reference to theattached drawing figures, wherein:

FIG. 1 is a block diagram of an exemplary computing environment suitablefor use in implementing the present invention;

FIG. 2 is a block diagram of an exemplary system for providing amulti-action button for mobile devices, in accordance with embodimentsof the present invention;

FIG. 3 is an illustrative graphical user interface display of amulti-action button, in accordance with an embodiment of the presentinvention;

FIG. 4 is a flow diagram showing a method for providing a multi-actionbutton for mobile devices, in accordance with an embodiment of thepresent invention.

DETAILED DESCRIPTION

The subject matter of the present invention is described withspecificity herein to meet statutory requirements. However, thedescription itself is not intended to limit the scope of this patent.Rather, the inventors have contemplated that the claimed subject mattermight also be embodied in other ways, to include different steps orcombinations of steps similar to the ones described in this document, inconjunction with other present or future technologies. Moreover,although the terms “step” and/or “block” may be used herein to connotedifferent components of methods employed, the terms should not beinterpreted as implying any particular order among or between varioussteps herein disclosed unless and except when the order of individualsteps is explicitly described.

Embodiments of the present invention can positively impact healthorganizations' key imperatives in a variety of ways. Embodiments of thepresent invention provide multi-action buttons on mobile devices thatcan be utilized by clinicians to improve response time and availability.

Referring now to the drawings in general, and initially to FIG. 1 inparticular, an exemplary computing system environment, for instance, amedical information computing system, on which embodiments of thepresent invention may be implemented is illustrated and designatedgenerally as reference numeral 100. It will be understood andappreciated by those of ordinary skill in the art that the illustratedmedical information computing system environment 100 is merely anexample of one suitable computing environment and is not intended tosuggest any limitation as to the scope of use or functionality of theinvention. Neither should the medical information computing systemenvironment 100 be interpreted as having any dependency or requirementrelating to any single component or combination of componentsillustrated therein.

Embodiments of the present invention may be operational with numerousother general purpose or special purpose computing system environmentsor configurations. Examples of well-known computing systems,environments, and/or configurations that may be suitable for use withthe present invention include, by way of example only, personalcomputers, server computers, hand-held or laptop devices, multiprocessorsystems, microprocessor-based systems, set top boxes, programmableconsumer electronics, network PCs, minicomputers, mainframe computers,distributed computing environments that include any of theabove-mentioned systems or devices, and the like.

Embodiments of the present invention may be described in the generalcontext of computer-executable instructions, such as program modules,being executed by a computer. Generally, program modules include, butare not limited to, routines, programs, objects, components, and datastructures that perform particular tasks or implement particularabstract data types. Embodiments of the present invention may also bepracticed in distributed computing environments where tasks areperformed by remote processing devices that are linked through acommunications network. In a distributed computing environment, programmodules may be located in local and/or remote computer storage mediaincluding, by way of example only, memory storage devices.

With continued reference to FIG. 1, the exemplary computing systemenvironment 100 includes a general purpose computing device in the formof a control server 102. Components of the control server 102 mayinclude, without limitation, a processing unit, internal system memory,and a suitable system bus for coupling various system components,including database cluster 104, with the control server 102. The systembus may be any of several types of bus structures, including a memorybus or memory controller, a peripheral bus, and a local bus, using anyof a variety of bus architectures. By way of example, and notlimitation, such architectures include Industry Standard Architecture(ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA)bus, Video Electronic Standards Association (VESA) local bus, andPeripheral Component Interconnect (PCI) bus, also known as Mezzaninebus.

The control server 102 typically includes, or has access to, a varietyof computer readable media, for instance, database cluster 104. Computerreadable media can be any available media that may be accessed by server102, and includes volatile and nonvolatile media, as well as removableand non-removable media. By way of example, and not limitation, computerreadable media may include computer storage media and communicationmedia. Computer storage media may include, without limitation, volatileand nonvolatile media, as well as removable and nonremovable mediaimplemented in any method or technology for storage of information, suchas computer readable instructions, data structures, program modules, orother data. In this regard, computer storage media may include, but isnot limited to, RAM, ROM, EEPROM, flash memory or other memorytechnology, CD-ROM, digital versatile disks (DVDs) or other optical diskstorage, magnetic cassettes, magnetic tape, magnetic disk storage, orother magnetic storage device, or any other medium which can be used tostore the desired information and which may be accessed by the controlserver 102. Communication media typically embodies computer readableinstructions, data structures, program modules, or other data in amodulated data signal, such as a carrier wave or other transportmechanism, and may include any information delivery media. As usedherein, the term “modulated data signal” refers to a signal that has oneor more of its attributes set or changed in such a manner as to encodeinformation in the signal. By way of example, and not limitation,communication media includes wired media such as a wired network ordirect-wired connection, and wireless media such as acoustic, RF,infrared, and other wireless media. Combinations of any of the abovealso may be included within the scope of computer readable media.

The computer storage media discussed above and illustrated in FIG. 1,including database cluster 104, provide storage of computer readableinstructions, data structures, program modules, and other data for thecontrol server 102. The control server 102 may operate in a computernetwork 106 using logical connections to one or more remote computers108. Remote computers 108 may be located at a variety of locations in amedical or research environment, for example, but not limited to,clinical laboratories, hospitals and other inpatient settings,veterinary environments, ambulatory settings, medical billing andfinancial offices, hospital administration settings, home health careenvironments, and clinicians' offices. Clinicians may include, but arenot limited to, a treating physician or physicians, specialists such assurgeons, radiologists, cardiologists, and oncologists, emergencymedical technicians, physicians' assistants, nurse practitioners,nurses, nurses' aides, pharmacists, dieticians, microbiologists,laboratory experts, genetic counselors, researchers, veterinarians,students, and the like. The remote computers 108 may also be physicallylocated in non-traditional medical care environments so that the entirehealth care community may be capable of integration on the network. Theremote computers 108 may be personal computers, mobile devices, servers,routers, network PCs, peer devices, other common network nodes, or thelike, and may include some or all of the components described above inrelation to the control server 102. The devices can be personal digitalassistants or other like devices.

Exemplary computer networks 106 may include, without limitation, localarea networks (LANs) and/or wide area networks (WANs). Such networkingenvironments are commonplace in offices, enterprise-wide computernetworks, intranets, and the Internet. When utilized in a WAN networkingenvironment, the control server 102 may include a modem or other meansfor establishing communications over the WAN, such as the Internet. In anetworked environment, program modules or portions thereof may be storedin the control server 102, in the database cluster 104, or on any of theremote computers 108. For example, and not by way of limitation, variousapplication programs may reside on the memory associated with any one ormore of the remote computers 108. It will be appreciated by those ofordinary skill in the art that the network connections shown areexemplary and other means of establishing a communications link betweenthe computers (e.g., server 102 and remote computers 108) may beutilized.

In operation, a user may enter commands and information into the controlserver 102 or convey the commands and information to the control server102 via one or more of the remote computers 108 through input devices,such as a keyboard, a pointing device (commonly referred to as a mouse),a trackball, or a touch pad. Other input devices may include, withoutlimitation, microphones, satellite dishes, scanners, or the like.Commands and information may also be sent directly from a remotehealthcare device to the control server 102. In addition to a monitor,the control server 102 and/or remote computers 108 may include otherperipheral output devices, such as speakers and a printer.

Although many other internal components of the control server 102 andthe remote computers 108 are not shown, those of ordinary skill in theart will appreciate that such components and their interconnections arewell known. Accordingly, additional details concerning the internalconstruction of the control server 102 and the remote computers 108 arenot further disclosed herein.

With reference to FIG. 2, a block diagram is illustrated that shows anexemplary computing system architecture for implementing embodiments ofthe present invention. It will be appreciated that the computing systemarchitecture shown in FIG. 2 is merely an example of one suitablecomputing system and is not intended as having any dependency orrequirement related to any single module/component or combination ofmodules/components.

The computing system 200 includes one or more user devices 210 (e.g., amobile communication device), network 230, and health information system240. User device 210 receives and displays data, such as alerts, fromhealth information system 240 and communicates or otherwise makes thedata available to multi-action engine 220. User device 210 also allows aclinician to respond to the alerts as well as communicate with otherclinicians (e.g., text, voice communication, e-mail).

Multi-action engine 220 may reside on one or more computing devices,such as, for example, the control server 102 described above withreference to FIG. 1, user device 210, as shown in FIG. 2, or healthinformation system 240. By way of example, the control server 102includes a computer processor and may be a server, personal computer,desktop computer, laptop computer, handheld device, mobile device,consumer electronic device, or the like. Multi-action engine 220comprises, in various embodiments, alert component 222, multi-actionbutton component 224, and display component 224.

In one embodiment, alert component receives an alert on a mobile deviceassociated with a clinician. For example, the alert may be an alertassociated with a patient in healthcare facility. The alert may be sentto multiple clinicians associated with the healthcare facility. Thealert may require acknowledgement or further action from one or more ofthe clinicians. The further action may be escalating the alert toanother clinician. Escalating the alert may require a voicecommunication or text message to another clinician. Unfortunately, eachof these actions, when made individually, waste valuable time.Interfaces displaying these actions individually appear cluttered andconfusing to clinicians, wasting additional valuable time.

In one embodiment, multi-action button component 224 determines amulti-button that corresponds to the alert. For example, one alert maybe more critical than another alert. The critical alert may requireadditional escalation or actions that can be integrated into amulti-action button that accomplishes the required escalations andactions. Display component 226 displays the multi-action button on themobile device.

In one embodiment, the multi-action button further corresponds to a roleassociated with the clinician. For example, the role of a clinician mayinfluence the escalation or actions that are integrated into amulti-action button. A medical assistant acknowledging an alert may,when acknowledging a particular alert, need to escalate the alert to thenursing staff, the attending physician, or even the critical responseteam. Another clinician may be required, upon acknowledging a particularalert, to take vitals that are entered into the medical device andpopulated into the EMR associated with that patient. In this example,acknowledging the alert may also automatically open a workflow directingthe clinician to take the required vitals. In one embodiment, themulti-action button further corresponds to a proximity or locationassociated with the clinician. For example, the proximity or location ofa clinician may make one clinician better situated to acknowledge andrespond to an alert than another clinician. In this example, theclinician that is not well situated may have a multi-action button that,upon acknowledging the alert, escalates the alert to the clinician thatis better situated to respond to the alert.

In one embodiment, the multi-action button further corresponds to apatient associated with the alert. The patient may have particularrequirements or preferences in which clinicians an alert is escalatedto. In this case, the clinician acknowledging the alert may have amulti-action button that includes escalating the alert to the requiredor preferred clinicians. For clarity, in any of the embodimentsdescribed herein, such a button may include segmented functionality suchthat when one portion of the button is selected, one action is taken,while another portion of the button is selected, another action istaken. Continuing the above example, portions of the button mayacknowledge and escalate (i.e., call or text message) to otherclinicians that may or may not be identified by a particular portion ofthe button. In one embodiment, the multi-action button furthercorresponds to a proximity or location associated with other clinicians.

In one embodiment, the multi-action button further corresponds to anavailability associated with the clinician or other clinicians. Forexample, portions of the multi-action button may allow the respondingclinician to acknowledge the alert and escalate to available clinicians.Portions of the multi-action button may identify available cliniciansand may allow the responding clinician to simultaneously acknowledge thealert and call or text message the appropriate identified, availableclinician.

Referring now to FIG. 3, an illustrative graphical user interface (GUI)300 depicts a multi-action button, in accordance with embodiments of thepresent invention. GUI 300 includes alert display area 310 that displayson alert on the mobile device. The alert display area 310 includes, inone embodiment, an alert level 312. In another embodiment, alert displayarea 310 includes information 314 specific to the alert that may assistthe clinician in determining whether to acknowledge and/or escalate thealert. In one embodiment, GUI 300 includes a reject button 320 forrejecting the alert. Rejecting the alert may cause the alert to becommunicated or escalated to another clinician. In one embodiment, GUI300 includes a patient information display area 316 that displaysinformation associated with a patient corresponding to the alert. In oneembodiment, patient display area 316 includes location information 318that displays a location associated with the patient and/or alert. Inone embodiment, GUI 300 includes a multi-action display area thatdisplays a multi-action button 330 that corresponds to the alert and arole associated with the clinician.

The multi-action button 330 may be segmented such that differentfunctions are provided by each segment. For example, segment 332 ofmulti-action button 330 accepts the alert and calls another clinician.In one embodiment, the second clinician that is called or who the alertis escalated to is identified by segment 332 so the determination of whoto call or escalate the alert to is automatically made for the firstclinician. Similarly, segment 336 of multi-action button 330 accepts thealert and opens a text messaging application for the first clinician totext message a second clinician regarding the alert. In one embodiment,a text message is automatically prepared and communicated to the secondclinician based on the alert and/or role of the clinician. In anotherembodiment, the recipient of the text message is identified by segment336 so the determination of who to text message or escalate the alert tois automatically made for the first clinician. In one embodiment, athird segment 334 of multi-action button 330 accepts the alert but takesno further action. Such acceptance may inform other clinicians that thefirst clinician is responding to the alert so the other clinicians donot lose time responding to an alert that is already accounted for. Ascan be appreciated, multi-action button 330 can be segmented into anynumber of segments streamlining the workflow for the clinician andbuilding escalation intelligence into the display and function of thesegments to ensure proper protocols are followed.

Referring now to FIG. 4, an illustrative flow diagram 400 is shown of amethod for providing a multi-action button for mobile devices, inaccordance with embodiments of the present invention. At step 410, analert is received at a mobile device associated with a clinician. Amulti-action button is determined, at step 420 that corresponds to thealert. The multi-action button may further correspond to a roleassociated with the clinician. At step 430, the multi-action button isdisplayed on the mobile device.

Many different arrangements of the various components depicted, as wellas components not shown, are possible without departing from the scopeof the claims below. Embodiments of our technology have been describedwith the intent to be illustrative rather than restrictive. Alternativeembodiments will become apparent to readers of this disclosure after andbecause of reading it. Alternative means of implementing theaforementioned can be completed without departing from the scope of theclaims below. Certain features and subcombinations are of utility andmay be employed without reference to other features and subcombinationsand are contemplated within the scope of the claims.

Having thus described the invention, what is claimed is:
 1. One or morenon-transitory computer storage media storing computer-executableinstructions that, when executed by one or more computing devices, causethe one or more computing devices to perform a method, the methodcomprising: generating an alert on a user interface of a mobile deviceassociated with a clinician, wherein the alert is specific to a patientin a medical facility, wherein the clinician is assigned to the patient,and wherein the alert comprises a multi-action user interface on themobile device, wherein the multi-action user interface includes at leastone action button; receiving a selection of the at least one actionbutton via the multi-action user interface; and executing afunctionality corresponding to the at least one action button selected,wherein the functionality comprises escalation of the alert to one ormore other clinicians.
 2. The media of claim 1, wherein the at least oneaction button comprise one or more of: a button that functions to rejectan alert, a button that functions to accept an alert, a button thatfunctions to accept the alert and initiate a phone call, and a buttonthat initiates a message screen.
 3. A computer system comprising aprocessor coupled to a non-transitory computer storage medium, thenon-transitory computer storage medium having stored thereon a pluralityof computer software components executable by the processor, thecomputer software components comprising: an alert component forgenerating an alert on the user interface of a mobile device associatedwith a clinician, wherein the alert is related to a patient in a medicalfacility, and wherein the clinician is assigned to the patient; amulti-action user interface component for determining a multi-actionuser interface for display on the user interface of the mobile device,the multi-action user interface comprising at least one action buttoncorresponding to the alert, wherein the multi-action user interfacecomponent determines the at least one action button integrated into themulti-action user interface based on an availability status associatedwith other clinicians; and a display component for displaying themulti-action user interface on the mobile device, wherein the system isconfigured to receive a selection of the at least one action button andprovide a distinct function associated with the selected at least oneaction button, wherein the distinct function associated with theselected at least one action button is an escalation of the alert to oneor more other clinicians.
 4. The system of claim 3, wherein themulti-action user interface component determines the at least one actionbutton integrated into the multi-action user interface based on aproximity or location associated with other clinicians. 5.Non-transitory computer storage media having computer-executableinstructions embodied thereon that, when executed, provide a graphicaluser interface (GUI) for mobile devices, the GUI comprising: an alertdisplay area that displays an alert specific to a patient in a medicalfacility on a mobile device associated with a clinician wherein theclinician is assigned to the patient; a multi-action display area thatdisplays at least one action button that corresponds to the alert; and amessage action area configured to facilitate communication between theclinician and one or more other clinicians, where communication isrelated to the alert; wherein, upon selection of the at least one buttonby the clinician, at least one distinct function is provided, wherein atleast one distinct function includes an escalation of the alert to oneor more other clinicians.
 6. The media of claim 5, wherein the GUIfurther comprises a patient information display area that displaysinformation associated with a patient corresponding to the alert.
 7. Themedia of claim 5, wherein the GUI further comprises a display area thatdisplays a button for rejecting the alert and causing the alert to becommunicated or escalated to another clinician.
 8. The media of claim 5,wherein the at least one distinct functions comprises initiating a callto another clinician and initiating a message application forcommunicating a message associated with the alert.
 9. The media of claim1, wherein the multi-action user interface is a pop-up.
 10. The media ofclaim 9, wherein the pop-up overlies other content displayed on themobile device user interface.
 11. The media of claim 1, where in themulti-action user interface comprises a patient information display areathat displays information associated with the patient to which the alertrelates, including at least one of the patient's name and locationinformation.
 12. The media of claim 1, wherein the multi-action userinterface comprises an alert information display area that displaysinformation regarding the alert, including at least one of the alertname, and alert severity.
 13. The media of claim 2, further comprisingreceiving a selection of the button that functions to reject an alertand forwarding the alert to another clinician assigned to the patient.14. The media of claim 2, further comprising receiving a selection ofthe button that functions to accept the alert and notifying at least oneclinician assigned to the patient of the acceptance.
 15. The media ofclaim 5, wherein the alert display area comprises the message actionarea.
 16. The media of claim 5, wherein the message action area displaysinformation regarding the patient and information regarding the alertalong with a message communicated between caregivers.
 17. Non-transitorycomputer storage media storing computer-executable instructions that,when executed by one or more computing devices, cause the one or morecomputing devices to perform a method, the method comprising: generatinga multi-action user interface on a user interface of a mobile deviceassociated with a clinician, the multi-action user interface comprising:at least one action button; a description of a medical alert related toa patient associated with the clinician; and an area identifying thepatient; receiving a selection of the at least one action button via themulti-action user interface; and executing a functionality correspondingto the selected at least one action button, including dismissing themulti-action user interface when the at least one action button isselected, wherein the functionality comprises escalation of the medicalalert related to the patient to one or more other clinicians.
 18. Themedia of claim 17, wherein the multi-action user interface is a pop-upmessage.
 19. The media of claim 18, wherein the multi-action userinterface overlies other elements of the user interface of the mobiledevice.
 20. The media of claim 5, wherein selection of the alertprovides an alert detail interface specific to the alert.
 21. The mediaof claim 1, further comprising providing the alert with at least asecond alert in an alert list interface.
 22. The media of claim 21,wherein the alert list interface further comprises one or moreadditional item buttons.